hi,

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "jr" <cre### [at] gmailcom> wrote:
>
> > but how will a numpty like self know how to select?
>
> You won't.  It will be one those fun mystery things, like a grab-bag, an egg
> hunt, voting.  Or dating.

fun, huh?


> Actually, part of the idea I had, which is somewhat demonstrated in the stuff I
> posted for TdG, is that, while not self-documenting, the code can be made to be
> "self-documentable" - in that, the verbose feature embedded into all of the
> macros could be turned on by such an array instantiation macro, and then you'd
> generate a list of entries upon execution.  Really, the idea was to have them
> available for random selection...

for supplementary info perhaps.  but before the parser can spit out info, I
already need to have a scene, no?  so, I would need (some) information up front.


> > I do hope that there will a
> > few introductory paragraphs discussing, and a small table laying out, the
> > principal (POV-Ray) components making "granite"; their role and useful parameter
> > ranges, etc.
>
> Could do that, or issue a #warning depending on values of macro parameters.
> Might just imply correct values by using min/max in macro definition, or
> comments.
>
> I agree, but I can see the line between "include file" and "geology textbook"
> becoming rapidly blurred.

maybe you misread, maybe I put it poorly.  "geology textbook" -- I'm sure that
some "background" info for each variant would be nice to have, to help
contextualise.  what I tried to say is I'd like to read "why we fake granite in
POV the way we do, how do we work around the limitations of the tools in the
box, this POV-Ray feature is used because ..." etc.

note to Thomas: _please_ correct the spelling to 'mahogany'.


regards, jr.

Post a reply to this message